• Resolves: #

Summary

We've long assumed usage of the public schema in PostgreSQL, but this is a more of a legacy approach these days. Since pgsql 15 it's no longer the default behavior. Rather than using workarounds to toggle on and use the older approach, we can migrate to the modern approach.

This is a backwards-compatible fix because it only affects the installation code path, which never runs again after initial setup. Existing installations continue working unchanged in public, while new installations benefit from better schema isolation and avoid the PostgreSQL 15+ permission issue entirely.

Separate follow-ups:

• Update database configuration docs (i.e. drop public / add what's needed if/when relying on manual user creation)
• Add instructions to help existing installations confirm which approach they have (e.g. SELECT schemaname FROM pg_tables WHERE tablename LIKE 'oc_%' LIMIT 1;)
• Possibly add instructions on switching

TODO

• Tests

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)